Nice and quiet here. You bring a real issue to the table and no adequate answers. This is not a hard problem to reproduce MS. I'm on 2013 CU9 and very frustrated that it's not working like it did in Exchange 2010 and easily showed up in my logs. My massive
list of Class C addresses are being ignored and not logged in FrontEnd or Hub logs.
I do see Block List Provider working properly in my FrontEnd\AgentLog --- just no locally defined IP's via
add-ipblocklistentry or add-ipallowlistentry.
For folks who don't know that /16 (Class B) is not allowed anymore in 2013 via the add-ipblocklistentry command then see the following:
https://technet.microsoft.com/en-us/library/JJ200718(v=EXCHG.150).aspx
Go to 1min 20sec of this video. Thank God for this guy otherwise who knows these lovely new restrictions... there are so many from 2010 to 2013 like not able to log into imap or pop3 with an admin account, etc. The errors have to be better since these are
all new limitations.
Looks like I'm not the only one with this problem please help us MS to keep spammers away. Blocklist providers alone as my protection mechanism is not enough. I have over 3000 blocked /24 (Class C) addresses and over 500 /16 (Class B) ones. Thankfully I
figured out the /16 limitation but fix IPBlockListEntry please and IPAllowListEntry. It's ridiculous that this is not getting as much attention as it should. Spam is not going anywhere...
Not to tangent but then there's general bugs like IMAP not working with NTLM as described here: http://blogs.technet.com/b/mspfe/archive/2015/08/24/exchange-server-2013-cu9-watch-your-imap-clients.aspx
Thanks for listening and please consider quality, MS :)